|
Cubesat Space Protocol (CSP) is a small network-layer delivery protocol designed for Cubesats. The idea was developed by a group of students from Aalborg University in 2008, and further developed for the AAUSAT3 Cubesat mission successfully launched in 2013. The protocol is based on a 32-bit header containing both network and transport layer information. Its implementation is designed for, but not limited to, embedded systems such as the 8-bit AVR microprocessor and the 32-bit ARM and AVR from Atmel. The implementation is written in C and is currently ported to run on FreeRTOS and POSIX and pthreads-based operating systems such as Linux. Support for Mac OS X and Microsoft Windows will be available in version 1.1. The three-letter acronym CSP was originally an abbreviation for ''CAN Space Protocol'' because the first MAC-layer driver was written for CAN-bus. The physical layer has since been extended to include several other technologies, and the name was therefore extended to the more general Cubesat Space Protocol without changing the abbreviation. The protocol and the implementation is actively maintained by the students at Aalborg University and the spin-off company GomSpace. The source code is available under an LGPL license and hosted on GitHub. == Description == The Cubesat Space Protocol enables distributed embedded systems to deploy a service-oriented network topology. The layering of CSP corresponds to the same layers as the TCP/IP model. The implementation supports a connection oriented transport protocol (Layer 4), a router-core (Layer 3), and several network-interfaces (Layer 1–2). A service-oriented topology eases the design of satellite subsystems, since the communication bus itself is the ''interface'' to other subsystems. This means that each subsystem developer only needs to define a service-contract, and a set of port-numbers his system will be responding on. Furthermore, subsystem inter-dependencies are reduced, and redundancy is easily added by adding multiple similar nodes to the communication bus. Notable features include: * Simple API similar to Berkeley sockets. * Router core with static routes. Supports transparent forwarding of packets over e.g. spacelink. * Support for both connectionless operation (similar to UDP), and connection oriented operation (based on RUDP). * Service handler that implements ICMP-like requests such as ping and buffer status. * Support for loopback traffic. This can e.g. be used for Inter-process communication between subsystem tasks. * Optional support for broadcast traffic if supported by the physical interface. * Optional support for promiscuous mode if supported by the physical interface. * Optional support for encrypted packets with XTEA in CTR mode. * Optional support for HMAC authenticated packets with truncated SHA-1 HMAC. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Cubesat Space Protocol」の詳細全文を読む スポンサード リンク
|